| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.1.4.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.1.4 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_1_4_Manage_Problem_List |
| Title | CP.1.4 Manage Problem List (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Create and maintain patient-specific problem lists. |
| Purpose | A problem list may include, but is not limited to chronic conditions, diagnoses, or symptoms, injury/poisoning (both intentional and unintentional), adverse effects of medical care (e.g., drugs, surgical), functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay or the life of a patient, allowing documentation of historical information and tracking the changing character of problem(s) and their priority. The source (e.g., the provider, the system id, or the patient) of the updates should be documented. All pertinent dates are stored, including date noted or diagnosed, dates of any changes in problem specification or prioritization, and date of resolution. This might include time stamps, where useful and appropriate. The entire problem history for any problem in the list is viewable. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Create and maintain patient-specific problem lists.
A problem list may include, but is not limited to chronic conditions, diagnoses, or symptoms, injury/poisoning (both intentional and unintentional), adverse effects of medical care (e.g., drugs, surgical), functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay or the life of a patient, allowing documentation of historical information and tracking the changing character of problem(s) and their priority. The source (e.g., the provider, the system id, or the patient) of the updates should be documented. All pertinent dates are stored, including date noted or diagnosed, dates of any changes in problem specification or prioritization, and date of resolution. This might include time stamps, where useful and appropriate. The entire problem history for any problem in the list is viewable.
| CP.1.4#01 | SHALL |
The system SHALL provide the ability to manage, as discrete data, all active problems associated with a patient. |
| CP.1.4#02 | SHALL |
The system SHALL capture, maintain and render a history of all problems associated with a patient. |
| CP.1.4#03 | SHALL |
The system SHALL provide the ability to manage the status of each problem (e.g., active, inactive, resolved). |
| CP.1.4#04 | SHALL |
The system SHALL provide the ability to manage relevant dates including the onset date and date(s) of problem status change (e.g., inactivation or resolution date). |
| CP.1.4#05 | SHALL |
The system SHALL provide the ability to manage information about the chronicity duration (e.g., chronic, acute/self-limiting) of a problem. |
| CP.1.4#06 | SHOULD |
The system SHOULD provide the ability to manage information regarding the information source (i.e. informant) of the problem. |
| CP.1.4#07 | SHALL |
The system SHALL conform to function [[RI.1.1.17]] (Deprecate/Retract Record Entries) to enable the inactivation or deprecation of a problem. |
| CP.1.4#08 | MAY |
The system MAY provide the ability to update an inactive problem in order to re-activate it. |
| CP.1.4#09 | SHOULD |
The system SHOULD provide the ability to render the list in a user-defined sort order. |
| CP.1.4#10 | SHALL |
The system SHALL provide the ability to render only active problems. |
| CP.1.4#11 | SHOULD |
The system SHOULD provide the ability to link one or more problem(s) in the Problem list to encounters. |
| CP.1.4#12 | MAY |
The system MAY provide the ability to link one or more problem(s) in the Problem List to medications. |
| CP.1.4#13 | MAY |
The system MAY provide the ability to link one or more problem(s) in the Problem list to orders. |
| CP.1.4#14 | MAY |
The system MAY provide the ability to link one or more problem(s) in the Problem list to medical equipment. |
| CP.1.4#15 | MAY |
The system MAY provide the ability to link one or more problem(s) in the Problem list to prosthetic/orthotic devices. |
| CP.1.4#16 | MAY |
The system MAY provide the ability to link one or more problem(s) in the Problem list to notes. |
| CP.1.4#17 | SHALL |
The system SHALL provide the ability to link orders, medical equipment, prosthetic/orthotic devices, and medications to one or more codified problems. |
| CP.1.4#18 | SHALL |
The system SHALL provide the ability to capture free text problems and render them in a manner that distinguishes them from coded problem entries. |
| CP.1.4#19 | SHALL |
The system SHALL tag and render an indicator that interaction checking will not occur against free text problems. |
| CP.1.4#20 | SHALL |
The system SHALL provide the ability to capture a problem into the problem list using standardized coding schemas (e.g., ICD or SNOMED). |
| CP.1.4#21 | SHALL |
The system SHALL provide the ability to manage free text comments associated with the problem. |
| CP.1.4#22 | MAY |
The system MAY provide the ability to manage the severity of a problem using a standards based classification scheme. |
| CP.1.4#23 | SHOULD |
The system SHOULD provide the ability to link actions taken and outcomes with a problem. |
| CP.1.4#24 | dependent MAY |
The system MAY provide the ability to manage problems for known genetically based illnesses (e.g., single allele carrier status of a genetic trait or disease) according to scope of practice, organizational policy, and/or jurisdictional law. |
| CP.1.4#25 | dependent MAY |
The system MAY provide the ability to manage a known single allele carrier status of a genetic trait or disease according to scope of practice, organizational policy, and/or jurisdictional law, and subject to patient's preferences and consent. |
| CP.1.4#26 | SHOULD |
The system SHOULD provide the ability to manage the linking of problems on the problem list, i.e., creating hierarchies or nestings within the problem list. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.1.4",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Create and maintain patient-specific problem lists.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>A problem list may include, but is not limited to chronic conditions, diagnoses, or symptoms, injury/poisoning (both intentional and unintentional), adverse effects of medical care (e.g., drugs, surgical), functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay or the life of a patient, allowing documentation of historical information and tracking the changing character of problem(s) and their priority. The source (e.g., the provider, the system id, or the patient) of the updates should be documented. All pertinent dates are stored, including date noted or diagnosed, dates of any changes in problem specification or prioritization, and date of resolution. This might include time stamps, where useful and appropriate. The entire problem history for any problem in the list is viewable.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage, as discrete data, all active problems associated with a patient.</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://hl7.org/fhir/condition.html\">https://hl7.org/fhir/condition.html</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL capture, maintain and render a history of all problems associated with a patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage the status of each problem (e.g., active, inactive, resolved).</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://hl7.org/fhir/R5/condition-definitions.html#Condition.clinicalStatus\">https://hl7.org/fhir/R5/condition-definitions.html#Condition.clinicalStatus</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage relevant dates including the onset date and date(s) of problem status change (e.g., inactivation or resolution date).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage information about the chronicity duration (e.g., chronic, acute/self-limiting) of a problem.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage information regarding the information source (i.e. informant) of the problem.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[RI.1.1.17]] (Deprecate/Retract Record Entries) to enable the inactivation or deprecation of a problem.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to update an inactive problem in order to re-activate it.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render the list in a user-defined sort order.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render only active problems.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to link one or more problem(s) in the Problem list to encounters.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link one or more problem(s) in the Problem List to medications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link one or more problem(s) in the Problem list to orders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link one or more problem(s) in the Problem list to medical equipment.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link one or more problem(s) in the Problem list to prosthetic/orthotic devices.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#16</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link one or more problem(s) in the Problem list to notes.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#17</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to link orders, medical equipment, prosthetic/orthotic devices, and medications to one or more codified problems.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#18</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture free text problems and render them in a manner that distinguishes them from coded problem entries.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#19</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL tag and render an indicator that interaction checking will not occur against free text problems.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#20</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture a problem into the problem list using standardized coding schemas (e.g., ICD or SNOMED).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#21</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage free text comments associated with the problem.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#22</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the severity of a problem using a standards based classification scheme.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#23</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to link actions taken and outcomes with a problem.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#24</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage problems for known genetically based illnesses (e.g., single allele carrier status of a genetic trait or disease) according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#25</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage a known single allele carrier status of a genetic trait or disease according to scope of practice, organizational policy, and/or jurisdictional law, and subject to patient's preferences and consent.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.1.4#26</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage the linking of problems on the problem list, i.e., creating hierarchies or nestings within the problem list.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.1.4",
"version" : "2.1.0",
"name" : "CP_1_4_Manage_Problem_List",
"title" : "CP.1.4 Manage Problem List (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Create and maintain patient-specific problem lists.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "A problem list may include, but is not limited to chronic conditions, diagnoses, or symptoms, injury/poisoning (both intentional and unintentional), adverse effects of medical care (e.g., drugs, surgical), functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay or the life of a patient, allowing documentation of historical information and tracking the changing character of problem(s) and their priority. The source (e.g., the provider, the system id, or the patient) of the updates should be documented. All pertinent dates are stored, including date noted or diagnosed, dates of any changes in problem specification or prioritization, and date of resolution. This might include time stamps, where useful and appropriate. The entire problem history for any problem in the list is viewable.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-01",
"label" : "CP.1.4#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage, as discrete data, all active problems associated with a patient.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#1",
"satisfiedBy" : [
"https://hl7.org/fhir/condition.html"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-02",
"label" : "CP.1.4#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL capture, maintain and render a history of all problems associated with a patient.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-03",
"label" : "CP.1.4#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage the status of each problem (e.g., active, inactive, resolved).",
"satisfiedBy" : [
"https://hl7.org/fhir/R5/condition-definitions.html#Condition.clinicalStatus"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-04",
"label" : "CP.1.4#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage relevant dates including the onset date and date(s) of problem status change (e.g., inactivation or resolution date).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-05",
"label" : "CP.1.4#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage information about the chronicity duration (e.g., chronic, acute/self-limiting) of a problem.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-06",
"label" : "CP.1.4#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage information regarding the information source (i.e. informant) of the problem.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-07",
"label" : "CP.1.4#07",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[RI.1.1.17]] (Deprecate/Retract Record Entries) to enable the inactivation or deprecation of a problem.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-08",
"label" : "CP.1.4#08",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to update an inactive problem in order to re-activate it.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#7"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-09",
"label" : "CP.1.4#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render the list in a user-defined sort order."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-10",
"label" : "CP.1.4#10",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render only active problems.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#9"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-11",
"label" : "CP.1.4#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to link one or more problem(s) in the Problem list to encounters.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.4.3#10"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-12",
"label" : "CP.1.4#12",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link one or more problem(s) in the Problem List to medications."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-13",
"label" : "CP.1.4#13",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link one or more problem(s) in the Problem list to orders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-14",
"label" : "CP.1.4#14",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link one or more problem(s) in the Problem list to medical equipment."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-15",
"label" : "CP.1.4#15",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link one or more problem(s) in the Problem list to prosthetic/orthotic devices."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-16",
"label" : "CP.1.4#16",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link one or more problem(s) in the Problem list to notes."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-17",
"label" : "CP.1.4#17",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to link orders, medical equipment, prosthetic/orthotic devices, and medications to one or more codified problems."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-18",
"label" : "CP.1.4#18",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture free text problems and render them in a manner that distinguishes them from coded problem entries."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-19",
"label" : "CP.1.4#19",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL tag and render an indicator that interaction checking will not occur against free text problems."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-20",
"label" : "CP.1.4#20",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture a problem into the problem list using standardized coding schemas (e.g., ICD or SNOMED)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-21",
"label" : "CP.1.4#21",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage free text comments associated with the problem."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-22",
"label" : "CP.1.4#22",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the severity of a problem using a standards based classification scheme."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-23",
"label" : "CP.1.4#23",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to link actions taken and outcomes with a problem."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.1.4-24",
"label" : "CP.1.4#24",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage problems for known genetically based illnesses (e.g., single allele carrier status of a genetic trait or disease) according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.1.4-25",
"label" : "CP.1.4#25",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage a known single allele carrier status of a genetic trait or disease according to scope of practice, organizational policy, and/or jurisdictional law, and subject to patient's preferences and consent."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.1.4-26",
"label" : "CP.1.4#26",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage the linking of problems on the problem list, i.e., creating hierarchies or nestings within the problem list."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.